This thesis presents the design and implementation of an accounting and status notification system for the LPRng print spooler. A solution using SNMP to query for needed accounting and status data is presented, a design built upon this, and an implementation produced. As the system derives from the requirements specification, it will make no attempt to solve all printer accounting problems or to offer compatibility with all printers, database management systems or print spoolers. However, several solutions for printer accounting are discussed and the best solution derived from the requirements specification will be chosen..

Title: Notification of animal welfareAuthor: Helen ÖhlundThe purpose of this study was to examine the routines of the county administrations in Sweden when it comes to receiving notification from the public about the welfare of animals. According to Jordbruksverket at least 50 % of the screening of animal welfare should be based on routine controls on existing farmers. Today the routine controls only reach a 43 % average for the whole country. A big part of today?s result depends on the amount of time it takes the administrators of animal welfare to process the notifications from the public.

The aim with our study has been to examine how preschool-staffs resonate about the Notification requirements according to Chapter 14, section 1, The Social Services Act, when a child fare badly or is suspected to fare badly: first, in relation to the municipality´s policies, but also in relation to the preschool staff´s actions in individual cases. Our study was conducted by qualitative research with semi-structured interviews. Total has two child´s nurses and six preschool-teachers, active within Växjö´s municipality, been interviewed. The result showed that the municipality´s guidelines on the one hand, underpinned by giving a prescribed pattern of behavior for preschool staff on how to act if the suspected that a child to fare badly. On the other hand preschool staff also experienced the guidelines diffuse as there were nothing described of the transition of how much they should document and observe before a notification could be initiated to the headmaster.

According to statistics, requirements management is identified as a major source of error to failed IT-projects. Moreover communication is identified as a factor affecting the require-ments management and can lead to deficiencies in the requirements. The requirements analyst is responsible for managing the requirements from the different stakeholders, act as a com-munication accommodator and to translate abstract requirements expressed by users to more specific requirements that developers can implement. The purpose of this thesis is to study the role of the requirements analyst to investigate the problems that may arise in working with requirements management.  To achieve the purpose we have performed a requirements management process in which we ourselves took the role as the requirements analysts. The requirements management process consisted of three phases: gather requirements, document requirements and validate require-ments.

The result from Requirements Engineering is a Requirements Specification. Characteristics of a good Requirements Specification are unambiguity, completeness, verifiability, consistency, modifiability, traceability, correctness and ranked for importance and/or stability.This work defines these quality attributes and answers the questions how to reach these attributes and the diffuculties which exist in this area.This work should be read to get an overwiew of the area Requirements Engineering and Requirements Specification..

In this Bachelor thesis I explore sound and room as elements in design of user interfaces, both theoretical and practical in a specific application domain, to identify some of the advantages and disadvantage associated with these elements. As application domain I studied email clients and their usage at home amongst students at Blekinge Institute of Technology. In the study I found an activity, which seems to be highly distributed in the physical room where the user is located. The activity was notification of email and could take place in an arbitrary location of the home. I then augmented this activity with ideas from my theoretical assumption about room and sound.

In this Bachelor thesis I explore sound and room as elements in design of user interfaces, both theoretical and practical in a specific application domain, to identify some of the advantages and disadvantage associated with these elements. As application domain I studied email clients and their usage at home amongst students at Blekinge Institute of Technology. In the study I found an activity, which seems to be highly distributed in the physical room where the user is located. The activity was notification of email and could take place in an arbitrary location of the home. I then augmented this activity with ideas from my theoretical assumption about room and sound. The result was a rule-based agent for notification of email, which primarily uses sound as interaction style..

Prioritisation of software requirements is a critical part of the development of software. Whichrequirements and in which order they will be developed is one of the main tasks that requirementprioritisation supports.There are different ways that a requirement prioritisation can be used, for example alone or in agroup and with different methods.The purpose of this report is to map out how you can carry out a requirement prioritisation alonewith different types of prioritisation methods and how you solve the problems that can arise whenprioritisting requirements. This is done by documenting the use of three different types of methodsthat can be execute alone. The methods are "100-dollar test", "Ranking" and "Top-tenrequirements".To be able to prioritise requirements, you need to establish which requirements you shall prioritise.The paper retrieves this information by interviewing stakeholders in the system and analysing theresult of the interviews and the execution of the requirement prioritisation.Three problems arose during that work and I present solutions on these problems. The problemswere 1) equivalent requirements when using the "100-dollar test", 2) low differentiation gradebetween the prioritised requirements in the "100-dollar test" and 3) that the requirements that wereprioritised weren't classified before the prioritisation, which leads to inaccuracies in the resultingprioritisation.The solution to the problems that the paper presents is to increase the amount of distributable unitsin the "100-dollar test" to 1000 per requirement, suggestions of classes of the requirements andthe combination of the methods "100-dollar test" and "ranking" to bypass the equivalentrequirements.The report is written in Swedish.Nyckelord: GoTRIS, requirements retrieval, requirements analysis, Viktoria Swedish ICT,requirements prioritisation, requirements, 100-dollar test, ranking, top 10 requirements..

Requirements engineering is a widespread topic in the research field of informatics. However, there is little research regarding lack of requirements documentation and how it is perceived. The same applies for how requirements engineering in retrospect can be implemented. This is a debated issue on blogs and forums but it has not been reflected in the research area.Therefore, this study concerns research questions regarding how the developers, testers and requirements analyst experience the lack of requirements documentation and how requirements engineering in retrospect can be implemented.To answer these questions, data collection has been conducted through qualitative interviews with individuals affected by this problem in their everyday work.This study has provided an explanation of how the problem is perceived and what the consequences are, both direct and indirect. The impacts are divided into three categories and are presented as, emotional consequences, system implications and consequences regarding re source consumption.

The environmental work of companies has become an incredibly important factor in achieving reduced levels of environmental pollution. For companies the work on environmental issues began in the 1980s. During this time companies also began to show interest for the personnel, an interest that was shown in the form of attempts to disclose personnel information in economics. Earlier this information was separated from the financial information, despite the fact that the revenues are created by the employees.The purpose of this paper is to examine how well companies with a notification or a permit today account for environmental- and personnel information in their director?s report.

Requirements engineering is a widespread topic in the research field of informatics. However, there is little research regarding lack of requirements documentation and how it is perceived. The same applies for how requirements engineering in retrospect can be implemented. This is a debated issue on blogs and forums but it has not been reflected in the research area.Therefore, this study concerns research questions regarding how the developers, testers and requirements analyst experience the lack of requirements documentation and how requirements engineering in retrospect can be implemented.To answer these questions, data collection has been conducted through qualitative interviews with individuals affected by this problem in their everyday work.This study has provided an explanation of how the problem is perceived and what the consequences are, both direct and indirect. The impacts are divided into three categories and are presented as, emotional consequences, system implications and consequences regarding re source consumption.

Requirements engineering is a widespread topic in the research field of informatics. However, there is little research regarding lack of requirements documentation and how it is perceived. The same applies for how requirements engineering in retrospect can be implemented. This is a debated issue on blogs and forums but it has not been reflected in the research area.Therefore, this study concerns research questions regarding how the developers, testers and requirements analyst experience the lack of requirements documentation and how requirements engineering in retrospect can be implemented.To answer these questions, data collection has been conducted through qualitative interviews with individuals affected by this problem in their everyday work.This study has provided an explanation of how the problem is perceived and what the consequences are, both direct and indirect. The impacts are divided into three categories and are presented as, emotional consequences, system implications and consequences regarding re source consumption.

Requirements engineering is a widespread topic in the research field of informatics. However, there is little research regarding lack of requirements documentation and how it is perceived. The same applies for how requirements engineering in retrospect can be implemented. This is a debated issue on blogs and forums but it has not been reflected in the research area.Therefore, this study concerns research questions regarding how the developers, testers and requirements analyst experience the lack of requirements documentation and how requirements engineering in retrospect can be implemented.To answer these questions, data collection has been conducted through qualitative interviews with individuals affected by this problem in their everyday work.This study has provided an explanation of how the problem is perceived and what the consequences are, both direct and indirect. The impacts are divided into three categories and are presented as, emotional consequences, system implications and consequences regarding re source consumption.

The building and plant sectors represent a large part of Sweden?s energy use. Putting energy requirements in public procurement as a tool for reducing energy consumption in the building and plant sectors is therefor an opportunity that operators can take advantage of. The aim of this thesis was to map the energy requirements in procurement that operators in the public sector use today in building and plant projects. The analysis was made with respect to if the energy requirements corresponded to the parts with large energy use in building and plant projects and also in which way energy requirements in procurement are written in the contract.

Requirements management is an important part of the software development process. The success of a project may depend on how this is handled. Even though several research studies indicates that more attention should be paid on non-functional requirements, the primary focus in practical projects still regards identifying functional requirements. Especially the prioritization of the non-functional requirements has been proven to be of great importance for the success of a project.This report investigates basics in agile requirements management involving opinions from experts from a software development company. This is done with help of existing literature and interviews with key actors involved in prioritization at the company.